Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.12](backport #38162) PoC: use pipeline generator #38486

Merged
merged 1 commit into from
Mar 21, 2024
Merged

[8.12](backport #38162) PoC: use pipeline generator #38486

merged 1 commit into from
Mar 21, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 20, 2024 •
edited by zube bot
Loading

Proposed commit message

Tasks

  • Enable when conditions.
    • GitHub comment - for individual stages and groups
    • GitHub labels - for individual stages
    • Changeset
    • Branches
  • Use catalog to generate the pipeline itself, rather than calling a python script on a pipeline.yaml file.
  • Support draft PRs.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #38162 done by [Mergify](https://mergify.com).

@v1v @mergify
Beats pipeline generator (#38162)
0089fb3 
This commit introduces a main pipeline generator similar to the one used with Jenkins #20104 to help with the migration to Buildkite.

Co-authored-by: Pavel Zorin <[email protected]>
Co-authored-by: Alexandros Sapranidis <[email protected]>
(cherry picked from commit 4b7467b)

# Conflicts:
#	.buildkite/hooks/pre-command
@mergify mergify bot requested review from a team as code owners March 20, 2024 15:20
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 20, 2024
@mergify mergify bot requested review from ycombinator and leehinman and removed request for a team March 20, 2024 15:20
@mergify mergify bot assigned v1v Mar 20, 2024
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Mar 20, 2024

Cherry-pick of 4b7467b has failed:

On branch mergify/bp/8.12/pr-38162
Your branch is up to date with 'origin/8.12'.

You are currently cherry-picking commit 4b7467b5c5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/auditbeat/scripts/unit-tests.sh
	new file:   .buildkite/buildkite.yml
	new file:   .buildkite/pipeline.py
	modified:   .buildkite/pipeline.yml
	new file:   .buildkite/scripts/generate_pipeline.sh
	new file:   auditbeat/buildkite.yml
	new file:   filebeat/buildkite.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/hooks/pre-command

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 20, 2024
@botelastic
Copy link

botelastic bot commented Mar 20, 2024

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 79 min 57 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@v1v v1v assigned pazone and unassigned v1v Mar 21, 2024
@pazone pazone merged commit 2f876d3 into 8.12 Mar 21, 2024
29 checks passed
@pazone pazone deleted the mergify/bp/8.12/pr-38162 branch March 21, 2024 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ycombinator ycombinator Awaiting requested review from ycombinator ycombinator is a code owner automatically assigned from elastic/elastic-agent-data-plane

@leehinman leehinman Awaiting requested review from leehinman leehinman is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees

@pazone pazone

Labels
backport conflicts There is a conflict in the backported pull request needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@elasticmachine @v1v @pazone